chore(deps): update sentry-javascript monorepo to v10 - #734
Conversation
|
Warning Review the following alerts detected in dependencies. According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.
|
78bc3a4 to
06fe1df
Compare
2dc3a58 to
79788e0
Compare
79788e0 to
0fb716e
Compare
8831d37 to
4f0363a
Compare
84862b1 to
68e1410
Compare
30a42c4 to
4a2dd53
Compare
db163e0 to
4f18732
Compare
3cbc85c to
f853963
Compare
bd05ca5 to
fd22aee
Compare
e3eef83 to
28d6725
Compare
28d6725 to
b1e740b
Compare
68c343f to
8f0f5cd
Compare
2adfbef to
0be0447
Compare
b28a493 to
173dcdc
Compare
62037dc to
fa9220d
Compare
d1041cb to
3fb4845
Compare
20a8cad to
3d08e0c
Compare
3d08e0c to
2a62e9f
Compare
2a62e9f to
141ebee
Compare
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
dc99737 to
8f7f9d9
Compare
8f7f9d9 to
917faf8
Compare
6e17cc1 to
c0ba3bb
Compare
1898d4b to
af3641c
Compare
af3641c to
e62a184
Compare
40d1b04 to
1783a1a
Compare
1783a1a to
732ad85
Compare
This PR contains the following updates:
^8.51.0→^10.0.0^8.51.0→^10.0.0Release Notes
getsentry/sentry-javascript (@sentry/node)
v10.73.0Compare Source
Important Changes
feat(v10/nextjs): Add
@sentry/nextjs/configentry point (#23766)withSentryConfigis now available from@sentry/nextjs/config, the path it moves to in v11. Importing it from@sentry/nextjsstill works on v10 but logs a warning once, so you can change yournext.configfile today and upgrade to v11 without touching it again.Other Changes
shouldHandleErroronsetupExpressErrorHandlerandsetupFasitfyErrorHandler(#23734)Internal Changes
Bundle size 📦
v10.72.0Compare Source
Important Changes
AI integrations no longer report errors that propagate to the caller (#23638, #23639, #23640)
Across all AI integrations (OpenAI, Anthropic, Google GenAI, LangChain, and LangGraph), the SDK no longer sends an event to Sentry for errors that the AI framework propagates to your code. Previously the instrumentation reported these as unhandled (
handled: false) before your own error handling ran, so an error your code caught still showed up in Sentry as an unhandled crash. The span is still marked as errored and the error still propagates, so reporting is left to your application: if your code does not handle the error, it reaches Sentry's global error handlers and is captured as unhandled, just like any other uncaught error. Errors that a provider surfaces as data on an otherwise successful response (such as Anthropic error-shaped responses or Google GenAI blocked content) are still captured, since your code never sees them propagate.feat(v10/cloudflare): Add
rpcTracePropagationBindings(#23737, #23738)The new
rpcTracePropagationBindingsoption names theenvbindings that outgoing RPC calls propagate trace context to. Strings match a binding name exactly, regular expressions match by pattern, and the default empty array propagates to nothing. RPC has no headers to carry trace context, so the SDK appends it as a trailing argument that only a Sentry-instrumented receiver removes again. List only the bindings whose receiver you know runs Sentry. Setting the option takes precedence overenableRpcTracePropagation, which is now deprecated. When you build with the Sentry Cloudflare Vite plugin, the bindings that resolve to this worker (its own Durable Objects and self service bindings) are derived from your wrangler config and added for you.Other Changes
_childSpanTimeoutID(#23673)Internal Changes
Work in this release was contributed by @ryanrho-mercor, @lux-in-tenebris-lucet, and @suhailopensource. Thank you for your contributions!
Bundle size 📦
v10.71.0Compare Source
Important Changes
The
enableLogsclient option now defaults totrue, so Sentry Logs work without any manual opt-in. Nothing is captured unless you call theSentry.logger.*APIs or add a log-forwarding integration (such asconsoleLoggingIntegration,pinoIntegration, or the winston transport), and you can setenableLogs: falseto opt out. Although a default change like this would normally land in a major release, we are shipping it in a minor after careful consideration, since it sends no data on its own and only takes effect once you actively use the logging APIs or a logging integration.Other Changes
scope.clear()method (#23231)Headersinstances (#23241)captureExceptionfrom scope, not fromClient(#23280)Internal Changes
Bundle size 📦
v10.70.0Compare Source
@sentry/node-cpu-profilerto 2.4.3 (#22992)@solidjs/routerv1 (#23163)onRequestpath (#22985)beforeSendwhile preserving session updates (#22819)meriyahissue forstandalonebuild (#23055)sourcemaps.disablewhenunstable_sentryVitePluginOptionsis set (#22966)<Routes>unmount (#22948)metricsfrom worker entry point (#23027)Internal Changes
@sentry/coredep to nextjs-16-userfeedback (#23009)sveltekit-3test (#23016)Work in this release was contributed by @davidmurdoch, @Jxxunnn, and @kamilogorek. Thank you for your contributions!
Bundle size 📦
v10.69.0Compare Source
Important Changes
instrumentAgentWithSentryfor Cloudflare Agents (#22786)The Cloudflare SDK adds a new
instrumentAgentWithSentryAPI for Cloudflare Agents. It works likeinstrumentDurableObjectWithSentryforAgentclasses from theagentsSDK and additionally creates spans for@callableRPC methods and automatically sets theconversationIdbased on the agent's name. When building with the Sentry Vite plugin, Agents are instrumented automatically (#22788).Other Changes
CREATE INDEXspans oncf_-prefixed tables (#22767)cf_spans stay filtered (#22766)sentry.originon logs fromSentryEffectLogger(#22806)@apm-js-collab/code-transformer-bundler-plugins(#22678)Internal Changes
Bundle size 📦
v10.68.0Compare Source
cache.keyon dataloader spans and capture redis delete operations ascache.remove(#22389)FirebaseInstrumentationto orchestrion (#22141)http.routeattribute tohttp.serverspans with parameterized routes (#22564)url.fullandurl.pathtohttp.serverspans (#22533)instrumentStateGraphAPI (#22491)url.fullattribute to core fetch instrumentation (#22436)stackFrameVariablesby variable name (#22526)@apm-js-collab/code-transformer-bundler-pluginsto 0.7.1 (#22497)functionToStringIntegrationcausing infinite recursions (#22527)baggage: "undefined"when DSC is missing (#22440)Internal Changes
v10to build and license-compliance branch filters (#22499)defineEnvVarsfrom@sveltejs/kit/env(#22390)Configuration
📅 Schedule: (UTC)
* 0-3 * * 1)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.